Test automation framework

A test automation framework is a set of assumptions, concepts and tools that provide support for automated software testing. The main advantage of such a framework is the low cost for maintenance. If there is change to any test case then only the test case file needs to be updated and the Driver Script and Startup script will remain the same. Ideally, there is no need to update the scripts in case of changes to the application.

Choosing the right framework/scripting technique helps in maintaining lower costs. The costs associated with test scripting are due to development and maintenance efforts. The approach of scripting used during test automation has effect on costs.

Various framework/scripting techniques are generally used:

  1. Linear (procedural code, possibly generated by tools like those that use record and playback)
  2. Structured (uses control structures - typically ‘if-else’, ‘switch’, ‘for’, ‘while’ conditions/ statements)
  3. Data-driven (data is persisted outside of tests in a database, spreadsheet, or other mechanism)
  4. Keyword-driven
  5. Hybrid (two or more of the patterns above are used)

The Testing framework is responsible for:[1]

  1. defining the format in which to express expectations
  2. creating a mechanism to hook into or drive the application under test
  3. executing the tests
  4. reporting results

Contents

Test automation interface

Test automation interface are platforms that provides a single workspace for incorporating multiple testing tools and frameworks for System/Integration testing of application under test. The goal of Test Automation Interface is to simplify the process of mapping tests to business criteria without coding coming in the way of the process. Test automation interface are expected to improve the efficiency and flexibility of maintaining test scripts.[2]

Test Automation Interface comprises of the following core modules:

Interface engine

Interface engines are built on top of Interface Environment. Interface engine comprises of a parser and a test runner. The parser is present to parse the object files coming from the object repository in to the test specific scripting language. Test runner deals with executing the test scripts using a test harness.[2]

Interface environment

Interface environment comprises of Product/Project Library and Framework Library. Framework Library have modules related with the overall test suite while the Product/Project Library have modules specific to the application under test.[2]

Object repository

Object repositories are a collection of UI/Application object data recorded by the testing tool while exploring the application under test.[2]

References

  1. ^ "Selenium Meet-Up 4/20/2010 Elisabeth Hendrickson on Robot Framework 1of2". http://www.youtube.com/watch?v=qf2i-xQ3LoY. Retrieved 2010-09-26. 
  2. ^ a b c d "Conquest: Interface for Test Automation Design". http://www.qualitycow.com/Docs/ConquestInterface.pdf. Retrieved 2011-12-11.